Systems and methods for providing a vending network

ABSTRACT

In one embodiment, a server includes a memory device and a processor configured to execute a set of instructions to communicate with a property management system, wherein the server receives transaction data from the property management system, the transaction data associated with a transaction and comprising a transaction type or a transaction class. The processor may inspect each transaction type or transaction class, compare each transaction type or transaction class to one or more allowed transaction types or transaction classes, and communicate approval of the respective transaction when the transaction type or transaction class has been previously approved to perform with the property management system.

TRADEMARKS

COCA-COLA® is a registered trademark of The Coca-Cola Company, Atlanta,Ga., U.S.A. Other names used herein may be registered trademarks,trademarks or product names of The Coca-Cola Company or other companies.

TECHNICAL FIELD OF THE INVENTION

This invention relates to a vending network, and more particularly tosystems and methods for providing a vending network.

BACKGROUND OF THE INVENTION

In the vending industry, coins and bills have been one manner used topay for vended goods and services. In this regard, when a vendingaccount is to be settled, coins and bills can be collected from vendingequipment, and the coins and bills can be reconciled with the physicalinventory to determine what was sold and how much money was collected.

In recent years, cashless payments, for example credit cards, havebecome an option for payments. In this regard, a user of vendingequipment may now be able to use cashless payments, in addition to coinand bill payments, for vended goods and services. In the case ofcashless payments, a cashless payment can typically be processed by athird party server. Subsequently, an electronic funds transfer (EFT) canremit the cashless payment received, less any transaction processingfees and/or other fees, to an operator of the vending equipment. Evenso, in some instances, the EFT may not reconcile an actual vend eventwith an associated actual cashless transaction. To further complicatematters, the vend sale amount may not match the EFT amount since feesmay be deducted from the cashless funds, and oftentimes, the EFTtransactions may represent an aggregated batch or bundling of multipletransactions, thus obscuring each individual vend transaction.

The processing of cashless transactions can cause numerous problems forprocessors handling cashless transactions, vendors offering goods and/orservices by way of a vending machine accepting cashless transactions,and others involved in the cashless transaction process. For example, inone settlement process, coins, bills, and cashless transactions may notbe timely reconciled with inventory since many cashless transactions maystill be stored in a vending machine or other associated data storagedevice. In other instances, cashless transactions may still be en routeto a third party server, not settled yet and/or aggregated with littleor no transaction level detail. Oftentimes, only after vend settlementis initiated, may an associated EFT transaction occur, which can furtherfrustrate the settlement process because of the aggregated nature ofEFTs.

In addition, the routing of cashless transactions to one or more thirdparty servers can also create an accountability problem. In someinstances, multiple items can be vended from a vending machine, and oneor more customers may attempt to pay with a cashless implement, such asa credit or debit card. However, in such instances, there is noguarantee that a vending equipment operator will ever see funds forvends paid for by cashless transactions, and no further guarantee that acustomer was correctly charged for the vended goods and/or services. Assuch, there may be little or no accountability as to when vends occurredor what was charged to the customer. Moreover, there may be little or noaccountability as to whether a customer was timely and accuratelycharged, and little or no assurance that a vending equipment operatortimely received the correct funds for vends paid for by cashlesstransactions.

Furthermore, a problem exists in auditing third party servers to verifyaccuracy and/or correctness of cashless transactions. In this regard,cashless transaction vending can lack oversight, accountability,auditing controls, and the ability to control how a device in thevending equipment operates and how data is communicated with or betweenvarious servers or other data processing devices.

Another problem occurs when route personnel attempt to reconciletransaction amounts and inventory at a vending equipment location. Insome instances, the amount of bills, coins, cashless vends, andinventory must be known at the same point in time. As related tocashless transactions, this means knowing what the value of eachtransaction is without any fees removed, knowing which of the cashlesstransactions have been settled, and also knowing which of the settledcashless transactions have a corresponding EFT record indicating that anoperator of the vending equipment has been paid for the cashlesstransactions. Without this level of detail, it may be unlikely that anaccurate or timely vending equipment settlement can be performed withouterror across multiple vending equipment locations. For vending equipmentin global locations, the settlement process may not be performedefficiently.

Therefore, a need exists for systems and methods for providing a vendingnetwork.

SUMMARY OF THE INVENTION

Some or all of the above needs can be addressed by various embodimentsof the invention. Embodiments of the invention can provide systems andmethods for providing a vending network.

In one embodiment, a system for providing a vending network can beimplemented. The system can include at least one transaction-type deviceassociated with a vending machine, wherein the at least onetransaction-type device is operable to facilitate cash transactionsand/or cashless transactions associated with one or more products orservices offered by the vending machine. The system can also include atleast one server operable to communicate with the at least onetransaction-type device, wherein the at least one server is operable toreceive data associated with the transactions. Furthermore, the systemcan include at least one vend settlement server operable to communicatewith the at least one server, wherein the at least one vend settlementserver can settle some or all of the transactions.

In another embodiment, a method for providing a vending network can beimplemented. The method can include receiving inputs for cashtransactions and/or cashless transactions from a plurality oftransaction-type devices associated with respective vending machines. Inaddition, the method can include transmitting transaction dataassociated with some or all of the transactions to at least one server.Moreover, the method can include settling some or all of thetransactions via at least one vend settlement server.

In yet another embodiment, a system for providing a vending network canbe implemented. The system can include at least one transaction-typedevice associated with a vending machine, wherein the at least onetransaction-type device is operable to facilitate cash transactionsand/or cashless transactions associated with one or more products orservices offered by the vending machine. In addition, the system caninclude at least one server operable to communicate with the at leastone transaction-type device, wherein the at least one server is operableto receive data associated with the transactions and is further operableto associate a unique identifier with each of the transactions.Moreover, the system can include at least one vend settlement serveroperable to communicate with the at least one server, wherein the atleast one vend settlement server can settle some or all of thetransactions.

In an additional embodiment, a method for providing a vending networkcan be implemented. The method can include receiving inputs for cashtransactions and/or cashless transactions from a plurality oftransaction-type devices associated with respective vending machines.The method can also include transmitting transaction data associatedwith some or all of the transactions to at least one server. Further,the method can include associating a respective unique identifier withsome or all of the transactions. Moreover, the method can includesettling some or all of the transactions via at least one vendsettlement server.

In yet another embodiment, a vending network can be provided. Thevending network can include at least one server operable to receiveinputs for cash transactions and/or cashless transactions from aplurality of transaction-type devices associated with respective vendingmachines. Furthermore, the vending network can include at least one vendsettlement server operable to communicate with the at least one server,wherein the at least one vend settlement server can settle some or allof the transactions. In addition, the vending network can include anoperator server operable to communicate with the at least one vendsettlement server to facilitate management of at least one operationalfunction comprising the following: vending machine fill-to-fillmanagement, route management, and vend transaction management.

Other embodiments and aspects of the invention are described in detailherein and are considered a part of the claimed invention. For a betterunderstanding of embodiments of the invention with features and aspects,refer to the description and to the drawings.

BRIEF DESCRIPTION OF THE FIGURES

The foregoing and other features, and aspects of the invention areapparent from the following detailed description taken in conjunctionwith the accompanying drawings in which:

FIG. 1 illustrates an example system for providing a vending network inaccordance with an embodiment of the invention.

FIG. 2 illustrates an example of a system that uses a reconciliationtoken during communications between a server switch and a third partyserver and/or a settlement engine in accordance with an embodiment ofthe invention.

FIG. 3 illustrates an example of a system that utilizes a settlementengine to provide operational and financial data processing for anoperator server in accordance with an embodiment of the invention.

FIG. 4 illustrates an example of a system that utilizes a server switchto interface to devices, vend settlement servers, third party servers,financial institutions, and other data services in accordance with anembodiment of the invention.

FIG. 5 illustrates an example of a system that uses a plurality ofserver switches, and provides for flexible financial transactionhandling and device network connectivity via the plurality of serverswitches and/or the settlement engine in accordance with an embodimentof the invention.

FIG. 6 illustrates an example of the server switch interfacing to aproperty management system (PMS) in accordance with an embodiment of theinvention.

FIG. 7 illustrates an example method for providing a vending network inaccordance with an embodiment of the invention.

FIG. 8 illustrates another example method for providing a vendingnetwork in accordance with an embodiment of the invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

As used herein, the term “transaction” can refer to a cash or cashlesspayment associated with a purchase of a good and/or service. Embodimentsof the invention are intended to cover any combination of cash and/orcashless payments or transactions as well as payments or transactionsrelating to any combination of goods and/or services.

As used herein, the terms “server switch” and “server” can be usedinterchangeably. Embodiments of the invention are intended to cover anycombination of servers, server switches, or other processing deviceswith similar functionality to a server or server switch.

As used herein, the terms “reconciliation token” and “unique identifier”can be used interchangeably. Embodiments of the invention are intendedto cover any type of unique identifier including, but not limited to, areconciliation token or any other device, code, or identifyinginstrument with similar functionality.

Referring now to FIG. 1, an example of a system such as a vendingnetwork system 100 in accordance with an embodiment of the invention isshown. Embodiments of the invention can provide systems and methods forproviding a vending network. Other embodiments of a vending network areshown in FIGS. 1-6. In general, embodiments of the invention can use oneor more reconciliation tokens to track or otherwise mark any number oftransactions handled by the vending network system 100 duringcommunications between at least one server switch and one or more thirdparty servers and/or a settlement engines.

In the embodiment shown in FIG. 1, a vending network system 100 caninclude one or more transaction devices 102A-N associated withrespective vending equipment 104A-N. Some or all of the transaction-typedevices 102A-N can be in communication via at least one network, such as106, with one or more server switches, such as 108A-N. In oneembodiment, one or more transaction-type devices 102A-N can be incommunication with each other via one or more networks, such as 106.

Transaction-type devices 102A-N can be any processor-type device, andmay be referred to individually as a data processing device. Some or alltransaction-type devices 102A-N can be operable to receive and transmitdata associated with at least one cash and/or cashless transaction, or aconsumer. Such data may be referred to as transaction data. Transactiondata can include, but is not limited to, vending equipment load-to-load(also referred to as fill-to-fill) information, vend transactionmatching and reconciliation processing data, electronic fund transaction(EFT) reconciliation data, cash vending transactions, cashless vendingtransactions, cashless transaction data, cash transaction data,transaction records, DEX data, MDB data, transaction refunds (alsoreferred to as reversals) data, accounting data, auditing data,electronic funds charge back data, route management data, businessmanagement data, and any other type of data associated with a vendingequipment transaction or a consumer. Examples of transaction-typedevices can include, but are not limited to, a cash transaction reader,a cashless transaction reader, a combination cash and cashlesstransaction reader, a RFID reader, a biometric reader, an energymanagement system (EMS)-type device, a vending machine controller (VMC),and any other type of payment transaction devices. In some instances, atransaction device can be manufactured by HP™, DELL™, IBM/LENOVO™, andGATEWAY™, and may operate software provided by MICROSOFT™, and LINUX™.

In one embodiment, a transaction-type device, such as 102A, can be apayment device operable to accept a cash and/or cashless payment from aconsumer, and further operable to facilitate the dispensing of goodsand/or services from associated vending equipment, such as 104A. Inanother embodiment, a transaction-type device, such as 102A, can be avending equipment controller operable to facilitate the operation ofassociated vending equipment, such as 104A.

Vending equipment 104A-N can include, but is not limited to, a productor beverage dispenser, a vending machine, a snack dispenser, a devicecapable of dispensing or providing a consumable food or drink item, adevice capable of dispensing or providing a non-consumable item, or adevice capable of facilitating purchase of a good and/or service.Vending equipment, such as 104A, can also be referred to individually asa vending machine. In some embodiments, vending equipment 104A-N mayconform to vending industry standards including, but not limited to, theNational Automatic Merchandising Association (NAMA) MDB specification,and the European Vending Association (EVA) DEX specification. In oneembodiment, vending equipment 104A-N can include a vending industrystandard-type multi-drop-bus (MDB) interface, and/or a data exchange(DEX) interface.

In one embodiment, multi-drop-bus (MDB) data can be collected fromvending equipment, such as 104A-N, and the collected MDB data used toform transaction data records. In this regard, MDB data can include, butis not limited to, inventory, product pricing, and other data duringvend events that can be combined with payment ID (for example a PINnumber or credit card number) to form a transaction record. In addition,MDB data can be collected during non-vend events and used to formtransaction records such as service requests, energy management records,and other types of transaction records.

In the embodiment shown in FIG. 1, a network 106 can be wired orwireless-type network, and may be more than one network to facilitateboth wired and wireless-type communications between system components.The network 106 shown in FIG. 1 is shown by way of example. Examples ofa network 106 can include, but are not limited to, a local area network(LAN), a wide area network (WAN), the Internet, a global network, awireless network, a wired network, and any combination thereof. Wirelessnetwork communications can be implemented, for example, by way of GSM,GPRS, CDMA2000, 1XRTT, EDGE, 802.11 types and kinds including but notlimited to ‘a’, ‘b’, ‘g’, ‘n’, 900 MHz, 2.4 GHz, 5 GHz, spread spectrum,open wireless standards, proprietary wireless techniques, 3G, 3.5G, 4Gtechnologies (‘G’ stands for generation), and any other wireless-typecommunication device, standard, or methodology. Wired networkcommunications can be implemented, for example, by way of Ethernet,Firewire, serial communications, USB, RS232, and any other wired-typecommunication device, standard, or methodology. In one embodiment, anetwork can be the Internet, which may be referred to as a globalnetwork.

In the embodiment shown, a server switch 108A can be a processor-basedplatform, such as a server. In one embodiment, a server switch 108A canbe operable to store a copy of some or all of transaction data receivedfrom one or more transaction devices 102A-N. The server switch 108A maystore some or all of the transaction data in an associated database ordata storage device, such as 110, 112, or 114. In another embodiment, aserver switch, such as 108A, can be operable to generate a uniqueidentifier, such as a reconciliation token, and associate the uniqueidentifier or token with or otherwise add the unique identifier or tokento a transaction record. In some embodiments, a server switch, such as108A, can generate and associate a unique identifier or reconciliationtoken with some or all transactions which may be transmitted via anetwork, such as 106, by the system 100.

As shown in FIG. 1, the system 100 can also facilitate communicationswith one or more servers 116, 118, 122 and/or third parties 120. In theembodiment shown, some or all of the transaction-type devices 102A-N canbe in communication with at least one of the following: a vendsettlement server 116, a data services server 118, a financialinstitution 120, a third party server 122, and/or any device associatedwith a third party. In this embodiment, a transaction-type device, suchas 102A, can transmit data via a network, such as 106, to a serverswitch, such as 108A. The server switch 108A can selectively transmitsome or all of the received data to another transaction-type device,such as 102N; another server switch, such as 108N; a vend settlementserver, such as 116; a data services server, such as 118; a financialinstitution, such as 120; a third party server, such as 122; or anyother device associated with a third party. Data received by a vendsettlement server 116, a data services server 118, a financialinstitution 120 and/or a third party server 122 can be stored in anassociated database, such as 109, or other data storage device.

In one embodiment, a transaction-type device, such as 102A, can transmitdata to a vend settlement server, such as 116, via a network, such as106, and server switch, such as 108A. Data initially received orotherwise collected by the transaction-type device 102A can betransmitted to the server switch 108A in a format such as a data packet124. The data can include, but is not limited to, vending equipmentload-to-load (also referred to as fill-to-fill) information, vendtransaction matching and reconciliation processing data, electronic fundtransaction (EFT) reconciliation data, cash vending transactions,cashless vending transactions, cashless transaction data, cashtransaction data, transaction records, DEX data, MDB data, transactionrefunds (also referred to as reversals) data, accounting data, auditingdata, electronic funds charge back data, route management data, businessmanagement data, and/or any other type of data associated with a vendingequipment transaction or a consumer. Ultimately, some or all of the datacan be transmitted by the server switch, such as 108A, to a vendsettlement server, such as 116.

In one embodiment, one or more reconciliation tokens can facilitateauditing some or all of the transaction data handled by one or more vendsettlement servers 116 and/or third party servers 122. For example, aserver switch, such as 108A, can communicate at least one reconciliationtoken with each transaction to a vend settlement server 116 and/or thirdparty server 122, and receive transaction data from the vend settlementserver 116 and/or third party server 122 in response to eachreconciliation token. In this example, a server switch 108A can transmitat least one reconciliation token in a data packet 126 to a vendsettlement server 116 and/or third party server 122. In response to thereceiving one or more reconciliation tokens, the vend settlement server116 and/or third party server 122 can transmit a data packet 128 withresponse data including the one or more reconciliation tokens to theserver switch 108A. Such response data can be compared to previouslytransmitted transaction data or other data previously stored in adatabase, such as 110, 112, or 114, or other data storage deviceassociated with the server switch 108A. In one embodiment, a vendsettlement server such as 116 can be referred to as a third party serverand can be audited in a similar manner described above.

Furthermore, in one embodiment, a server switch, such as 108A, can beoperable to switch or otherwise transfer one or more transaction recordsbetween various destination servers. For example, transaction datastored on a particular server can be transferred to another server byway of a server switch, such as 108A. Moreover, a server switch 108A canbe operable to issue a data packet 130 with one or more reconciliationtokens in response to transaction data received or transmitted by theserver switch 108A. In addition, a server switch 108A can be operable tomaintain at least one transaction database for storing transaction data,such as a plurality of databases including a KO database 110,reconciliation database 112, and device database 114.

In one embodiment, a server switch, such as 108A, can be operable tocontrol access to a network, such as 106, by inspecting each transactionreceived at the server switch 108A. For example, before passingtransaction data from a transaction-type device, such as 102A, to adestination location, the server switch 108A can check a database, suchas the device database 114, to ensure that the transaction-type device,for instance 102A, from which the transaction is received is allowed touse the network 106. If the transaction-type device 102A is not allowedto use the network 106, the transaction data is not forwarded to thedestination location and optionally the transaction-type device 102A canbe informed by the server switch 108A that access to the network 106 isdenied.

In another embodiment, a server switch, such as 108A, can be operable tocontrol the types or classes of transactions a particulartransaction-type device, such as 102A, is allowed to transmit on anetwork, such as 106. In this regard, the server switch 108A can inspectthe type or class of transaction being transmitted, compare eachtransaction type or class to one or more allowed types or classes oftransactions stored in a database, such as device database 114, anddetermine if such a transaction is allowed from the particulartransaction-type device 102A. For example, if a transaction-type device102A is deployed to accept a particular class of transactions, such ashotel room key cards, the server switch 108A can prevent or otherwiselimit all other transactions, such as non-hotel room key cards, frombeing used.

Referring to FIG. 2, an example system 200 for tracking one or moretransactions in a vending network in accordance with an embodiment ofthe invention is shown. The system 200 can be implemented using some orall of the system components shown in FIG. 1, and in this example, someof the system components of system 100 are utilized. In this embodiment,the system 200 can include a data flow which commence when atransaction-type device, such as 102A, can initiate communication with athird party server, such as 118, by way of server switch, such as 108A.For example, the transaction-type device 102A can generate and transmitat least one data packet, such as 124, which can include transactiondata that can be encrypted such that a third party server, such as 118,can decrypt the data by way of at least one decryption key. In someinstances, the encrypted transaction data can include other data, suchas KO data, and can be further encrypted wherein the server switch 108Acan decrypt the data by way of another decryption key. In any instance,the server switch 108A can receive the encrypted data, or data packet124, and after processing the encrypted data or data packet 124, thesever switch 108A can transmit a corresponding data packet, such as 126,to the third party server 122. After receipt and processing of the datapacket 126, the third party server 118 can transmit a corresponding datapacket, such as 128, to the server switch 108A, wherein the serverswitch 108A decrypts and processes the data. Processing of the data by aserver switch, such as 108A, can include some or all of the followingactivities: verifying that a transaction-type device, such as 102A, isauthorized to access a network, such as 106; verifying that atransaction-type device, such as 102A, is authorized to perform aparticular transaction type or class; generating at least onereconciliation token; and storing data, such as KO data, in a databaseor data storage device, such as 110, 112, and/or 114.

Referring back to the server switch, the server switch, such as 108A,can generate at least one data packet by either generating at least onenew reconciliation token if a particular transaction requires it (suchas when an initial authorization request is made) or identifying and/orretrieving a previously assigned reconciliation token (such as when athird party server 122 is communicating a response to transaction-typedevice, such as 102A). The data packet, for example 126, can include atleast one reconciliation token and previously received third party ortransaction data. In some instances, the previously received third partyor transaction data can be encrypted if desired. The data packet 128 canbe communicated to the third party server 122.

Referring to the third party server, upon receipt of the data packet126, the third party server, such as 122, can process the received datapacket 126. Such processing can include, but is not limited to,decrypting the encrypted packet and acting on the data, or storing areconciliation token and/or other associated transaction data in adatabase or data storage device, such as 110, 112, or 114.

During or after completion of processing the data packet 126 at thethird party server 122, the third party server 122 can wait for aresponse to be communicated to transaction-type device 102A. In thisregard, a data packet, such as 128, can be generated by the third partyserver 122 to include at least one previously received reconciliationtoken that was associated with the particular transaction at the serverswitch 108A, as well as response data from the third party server 122.In some instances, the response data from the third party server 122 canbe encrypted if desired).

The third party server 122 can communicate the data packet 128 to theserver switch 108A. The server switch 108A receiving the data packet 128can use at least one reconciliation token to verify that a predefinedtransaction state sequence is being followed, and can update one or morestate fields associated with the instant transaction. The server switch108A can update one or more databases as necessary, and/or otherwiseprocess the received data packet 128. The server switch 108A cancommunicate a corresponding data packet 130 to the transaction-typedevice 102A. The data packet 130 can be received at the transaction-typedevice, such as 102A, where the transaction-type device 102A can processthe data packet 130 and associated response data. In this example, datapackets 124, 126, 128, and 130 can be of the same or similar format.

In one embodiment, a state machine data structure can be established bya server switch, such as 108A, for a particular class of transaction. Inthis regard, the server switch 108A can determine if a particulartransaction-type device, such as 102A, is allowed to perform aparticular class of transaction (for example, a hotel room keycard-type-transaction) and prevent or otherwise limit thetransaction-type device 102A from performing certain types oftransactions (for example, RFID credit card-type transactions). Usingstate machine logic or a set of instructions, the server switch 108A canensure that a prescribed sequence of communications between thetransaction-type device 102A and the third party server 122 ismaintained.

For example, when a transaction-type device, such as 102A, facilitates asales or vending transaction at a vending machine, such as 104A, by wayof a user paying with a credit card, a state of the transaction can beas follows. Initially, a first state can be recorded by a server switch,such as 108A, as an initial authorization request by thetransaction-type device 102A. Another state can be a response to theinitial authorization request by a third party server, such as 122. Yetanother state can be a completed sales record communicated from thetransaction-type device 102A when the user completes the sales orvending transaction. Another state can be when the third party server122 acknowledges the receipt of the completed sales transaction recordcommunicated from the transaction-type device 102A.

In this embodiment, the state tracking capability of a server switch,such as 108A, related to each class of transactions and for eachindividual transaction can permit the server switch 108A to provideaccountability for some or all transactions. This can include, but isnot limited to, tracking which transactions are in a particular state ofprocessing, and instructing a transaction-type device, such as 102A, andan associated third party server, such as 122, to adhere to apredetermined sequence of communications (also referred to as “statemachine type logic”). In the case where a transaction sequence isunsuitable or otherwise incorrect, a server switch, such as 108A, canstop or delay a particular transaction from proceeding and/or send amessage to either or both the transaction-type device 102A and the thirdparty server 122. This feature can permit the server switch 108A tomaintain accountability of each transaction-type device 102A-N, eachthird party server, such as 122, and to also maintain oversight of themanner in which transaction-type devices, such as 102A-N, and anassociated third party server, such as 122, communicate to performcertain classes of transactions.

One aspect of using one or more state conditions to monitor, controland/or track transactions is that at any time a server switch, such as108A, can determine which transactions have been completed. In thisregard, such information can be used, for example, to more accuratelyidentify transactions that may appear to have been lost. Suchtransactions may have been authorized, but never settled, as such, thestate of these missing transactions is that the transactions may onlyhave been partially completed (no sales information, no settlement, noEFT, etc.). This aspect permits a user, via the server switch, such as108A, to identify possible issues related to payment for products and/orservices. In addition, the user can identify issues related to anynumber of transaction-type devices 102A-N, servers such as a third partyserver 122, and/or other issues related to transaction processing by thesystem 100.

Referring to FIG. 3, an example system 300 for providing a vendingnetwork in accordance with an embodiment of the invention is shown. Thesystem 300 can be implemented using some or all of the system componentsshown in FIG. 1, and in this example, some of the system components ofsystem 100 are utilized.

In the embodiment shown in FIG. 3, a vend settlement server, such as116, can provide some or all operational and financial data processingfor an associated operator server, such as 134. An operational servercan be operable to manage vending equipment, such as 104A-N, and/or oneor more associated vending routes. The vend settlement server 116 can beoperable to coordinate the reconciliation of coins, bills, cashlesstransactions, and other types of inventory management data. As shown,the vend settlement server 116 can communicate with the operator server134. With data provided by the vend settlement server 116, the operatorserver 134 can provide route management for vending equipment, such as104A-N, including, but not limited to, reporting, route management,accountability, service, financial management, business analysis, assetmanagement, product inventory management, and data processing. In thisregard, a vend settlement server such as 116 can be operable for moneyreconciliation, pre-cashless settlement processing (determining therevenue cashless transactions should produce), post settlementprocessing (determining the revenue actually received from cashlesstransaction processing—as an example from EFTS), and coordinate thedelivery of funds, inventory, and other vending equipment data to anassociated operator server such as 134.

In operation, the operator server 134 can communicate with the vendsettlement server 116. Initially, transaction data from one or moretransaction-type devices, such as 102A, and associated vendingequipment, such as 104A, can be received or otherwise collected by theserver switch 108A. The server switch 108A can communicate further asneeded or desired with a data services server, such as 118 and/or athird party such as a financial institution 120. As discussedpreviously, transaction data can be communicated by the server switch108A to the vend settlement server 116 for processing and/or storage.Optionally, a vend settlement server, such as 116, can utilize one ormore databases to store data as may be required or desired, such as atransaction database 109. In any instance, the vend settlement server116 can communicate with the operator server 134 to handle some or allof the following activities: reconciliation of coins, bills, cashlesstransactions, and other types of inventory management data; reporting;route management; transaction accountability; service; financialmanagement; business analysis; asset management; product inventorymanagement; data processing; money reconciliation; pre-cashlesssettlement processing (determining the revenue cashless transactionsshould produce); post settlement processing (determining the revenueactually received from cashless transaction processing—as an examplefrom EFTS); and coordinate the delivery of funds, inventory, and othervending equipment data.

In this manner, reconciliation of bills, coins, and cashlesstransactions can be synchronized with the product or inventory that aroute operators fills the vending equipment with, or otherwise restocksthe vending equipment with. Delays in processing certain types ofcashless transactions, such as credit card transactions, can result inless than 100% accountability of payment detail (bills, coins, andcashless revenues) at the time the route operator is restocking thevending equipment. As such, the ability to determine what has been soldand paid for can be difficult to determine at any given time andespecially when cashless transactions are delayed by processing, such aspending electronic funds transfers (EFTS). In addition, the inability toaccurately determine what has been purchased from the vending equipmentcan cause the route personnel to incorrectly select the restock productto load on to the route truck before traveling to the vending equipmentlocation, which may cause too much or too little restock product to becarried on the route for subsequent restocking.

In FIG. 4, an example system 400 for providing a vending network inaccordance with an embodiment of the invention is shown. The system 400can be implemented using some or all of the system components shown inFIG. 1, and in this example, some of the system components of system 100are utilized. In the system shown, a server switch 108A can be incommunication with a plurality of third party servers 122, such thirdparty servers 122 utilizing a plurality of databases, such astransaction database 109. At least one of the third party servers 122can be in communication with one or more financial institution servers120, and by way of server switch 108A in communication with a pluralityof transaction-type devices 102A-N. In this configuration, at least onethird party server 122 can process transactions from the plurality oftransaction-type devices 102A-N, and via server switch 108A can providetransaction level detail data and EFT level detail data to at least onevend settlement server 116, where such data is processed or otherwisereconciled with other data (non-cashless and other data) and then datacommunicated to the operator server 134.

In addition, optionally the server switch 108A can communicate with atleast one financial institution server 120A and/or at least one dataservices server 118. In this regard, the server switch 108A can processtransactions, providing as may be required and/or desired transactionlevel detail data, EFT level detail data, and/or other types of data ordetail data to at least one vend settlement server 116, wherein the vendsettlement server 116 with other data including data from at least onethird party server 122 can process data and communicate as necessarywith at least one operator server 134 to facilitate route management forvending equipment, such as 104A-N, including reporting, routemanagement, accountability, service, financial management, businessanalysis, asset management, product inventory management, and dataprocessing.

In the embodiment shown, a server switch, such as 108A can be incommunication with one or more transaction-type devices, such as 102A-N,at least one vend settlement server 116, one or more third party servers122, one or more financial institutions 120, and one or more dataservices servers 118. The transaction-type devices 102A-N cancommunicate different types of data, such data formatted in one or moredata packets, to the server switch 108A. For example, a data packet 124can include KO data and third party transaction data (encrypted ifnecessary). A second transaction-type device, such as 102B, maycommunicate formatted KO data illustrated as data packet 136. Theflexibility of the server switch 108A to accommodate a plurality ofdifferent types of data, associated data packets, and data formatspermits relevant data to be inspected and processed at the server switch108A, such as KO data, as well as allow, if necessary, third party data(encrypted and/or otherwise proprietary) to be transmitted by the serverswitch 108A to a destination third party server, such as 122, and/or toa vend settlement server, such as 116.

An aspect of this embodiment is that collection of data from a pluralityof transaction-type devices, such as 102A-N, at the server switch, suchas 108A, can be relatively homogeneous across the plurality of devices,such as 102A-N. This can be implemented by some embodiments regardlessof the type or purpose of the plurality of transaction-type devices.Another aspect of this embodiment is that oversight and accountabilityat the server switch, such as 108A and vend settlement server, such as116, can be relatively easily maintained due in part to relativelyhomogenous data being received at the server switch 108A.

In another embodiment, an aspect is the ability for third party serverssuch as third party server 122 to receive data from the sametransaction-type devices, such as 102A-N, in a format that allows thethird party server 122 to continue operating as designed. In otherwords, transaction-type device, such as 102A, is operable to send a datapacket (for instance, KO data and/or third party data) that can be bothunderstood by the server switch, such as 108A, and by the third partyserver, such as 122. This permits both servers, the server switch 108Aand the third party server 122, to function with minimal or no changes.This “shared data type function” can permit one or more third partieswith their own information technology (IT) infrastructure, perhapstailored to provide a particular product and/or service to their owncustomers, to use a vending network in accordance with an embodiment ofthe invention to both satisfy their third party data needs as well assatisfy needs of the server switch, such as 108A, a vend settlementserver, such as 116, and/or an operator server, such as 134.

Another aspect of this embodiment can permit one or more third partiesto provide various services to customers (web based and/or otherwise)from their own IT infrastructure while allowing a vending network inaccordance with an embodiment of the invention, managed by the serverswitch, such as 108A, to maintain accountability, audit ability of thenetwork, and utilize a vend settlement server, such as 116, to meet someor all of the needs of one or more vending route operators by way of anoperator server, such as 134, and vending equipment personnel that mayrely on the operator server 134 to operate or otherwise manage theirrespective businesses.

In one embodiment of a system for providing a vending network, asillustrated in FIG. 4, one or more databases, such as 109, 110, 112, and114, or data storage devices can be associated with either or both avend settlement server, such as 116, and/or the server switch, such as108A.

In one embodiment of a system for providing a vending network, asillustrated in FIG. 4, a vend settlement server, such as 116, caninitiate an audit of a third party server, such as 122. In this regard,a vend settlement server, such as 116, can generate and transmit one ormore reconciliation tokens to a third party server, such as 122, by wayof transmitting a data packet to the third party server 122, and thevend settlement server 116 can receive a data packet including aresponse from the third party server 122.

Another embodiment of a system for providing a vending network caninclude a combination of servers, wherein a server originating an auditof a third party server, such as 122, can either be a server switch,such as 108A, or a vend settlement server, such as 116, and a datapacket including a response from a third party server, such as 122, canbe sent to a non-originating server, such as either the server switch108A or a vend settlement server 116.

Referring to FIG. 5, an example system 500 for providing a vendingnetwork in accordance with an embodiment of the invention is shown. Thesystem 500 can be implemented using some or all of the system componentsshown in FIG. 1, and in this example, some of the system components ofsystem 100 are utilized. In this embodiment, the system 500 can includea plurality of server switches, such as 108A-N in communication with aplurality of transaction-type devices, such as 102A-N, and at least onevend settlement server, such as 116. The plurality of transaction-typedevices 102A-N can utilize one or more of the plurality of serverswitches 108A-N to communicate with various data processing equipment,such as financial institution 120, the vend settlement server 116,and/or other third party servers, such as 122. The system embodimentshown can provide relatively flexible financial transaction handling anddevice network connectivity. In this manner, different transaction-typedevices and server switches can be utilized to aggregate bills, coins,cashless, inventory, and/or other types and kinds of transaction data.

The flexibility and connectivity of the system embodiment shown canpermit in some instances, certain cashless transactions to be processedwhere a sale amount is known but the actual funds are not yet available.For example, on occasion certain cashless transaction types, such ascredit cards, may appear as a “good account” when authorized, but whenit comes time to settle the transaction with the actual sale amount, thesettlement process may sometimes fail. Such failures can occur forvarious reasons including the expiration of a credit card, an accountbeing closed sometime after authorization but before settlement, and formany other reasons. In addition, there can be typically about a 24-72hour delay from the time the settlement process occurs and the time thefunds are actually available.

These circumstances, in combination with the fact that operators ofvending equipment may need to synchronize coins, bills, and cashlesstransactions in a timely manner (often quicker then cashless funds areavailable) to facilitate route and inventory management, can provide aneed to track cashless transactions in a pre-settled state, apost-settled state, and/or by EFT summary detail.

Pre-settled cashless transaction can be characterized as transactionsthat have been completed at vending equipment, such as 104A-N, andinclude a sale amount and any associated vend detail but still have tobe communicated to a financial institution for settlement. Post-settledcashless transactions can be characterized as cashless transactions thathave been communicated to a financial institution for settlement butfunds may not be available. EFT summary detail can be characterized asthe actual funds available that have been deposited (wired into a bankaccount).

In operation, there may be times when pre-settled cashless transactiondetails (sales that have not been settled) need to be combined withcoins, and to reconcile vending equipment as well as to manageinventory. During other situations, post-settled cashless transactiondetail may need to be relied upon, and finally EFTs may be reconciled tobetter manage the operator business. In one embodiment, the variousstates and conditions related to cashless transaction handling can beaccommodated by the example system shown in FIG. 5.

As shown in FIG. 5, a financial institution, such as 120, can be incommunication with at least one server switch, such as 108A-N, and atleast one vend settlement server, such as 116. In this manner, thesystem 500 can handle various cashless transactions as well as provide aplurality of communication paths such that the server switches 108A-Nand the vend settlement server 116 can synchronize some or all of thecashless transactions in a variety of states. The system 500 can alsohandle EFTs, coins, and bills, thus facilitating route management ofvending equipment, products and service inventory, and/or financialaccountability at an operator server, such as 134.

Referring to FIG. 6, an example system for providing a vending networkin accordance with an embodiment of the invention is shown. The system600 can be implemented using some or all of the system components shownin FIG. 1, and in this example, some of the system components of system100 are utilized. In this embodiment, the system 600 can include atleast one server switch in communication with at least one propertymanagement system (PMS). For example in the embodiment shown in FIG. 6,server switch 108A can be in communication with property managementsystem 138. In one embodiment, a property management system can be usedin a hotel or other places to manage guest portfolios including check-inguests, assign rooms, accrue guest charges, and for performing otherservices. In another embodiment, a property management system can beused in a location where third party information is desired to bemanaged in a relatively secure location associated with the third party.

In one embodiment, the system 600 can process transactions associatedwith hotel room keys. For example, one or more hotel room key cards canbe utilized to allow hotel guests to use a respective hotel room keycard at one or more transaction-type devices, such as 102A-N. In someinstances, a hotel guest may desire to have a product or servicepurchase added to his or her portfolio or invoice managed by a propertymanagement system, such as 138. In this regard, by using his/her hotelroom key card, a guest can have his/her purchases at transaction-typedevices 102A-N billed to his/her room and pay for the vended productsand/or services when the hotel bill is paid.

In one embodiment, one or more transaction-type devices, such as 102A-N,can generate and send transaction data, such as data packets 124 shownin FIG. 1, to a server switch, such as 108A. In certain instances,property management may not want certain transaction data, such as hotelkey card data, to leave the premises for security reasons, and the useof a wide area network (WAN) configuration where a server switch islocated at a remote location may not be acceptable to propertymanagement. One aspect of a server switch, such as 108A, can be thelocation of the server switch at or on property owned or otherwisecontrolled by property management. In this manner, a server switch, suchas 108A, can communicate with a plurality of transaction-type devices,such as 102A-N, which may be hotel key card reading devices, and alsocommunicate with the property management system, such as 138.

In one embodiment, certain transaction data such as hotel key card datacan remain onsite, but other transaction data, such as credit cardtransactions, sales information, inventory, service, and other data maybe acceptable to communicate remotely. In this example, a first serverswitch, such as 108A, can communicate with one or more other serverswitches, such as 108N, and as necessary, to one or more vend settlementservers, such as 116, third party servers, such as 122, operatorservers, such as 134, and/or to other data processing equipment.

In one embodiment, a server switch, such as 108A, can be integrated intoat least one transaction-type device, such as 102A-N. In this example,at least one of a plurality of transaction-type devices, such as 102A-N,can function as a server switch in addition to performing variousfeatures and functions as a transaction-type device, such as 102A-N. Inthis regard, a system in accordance with an embodiment of the inventionmay implement one or more micro-type server switches with respectivetransaction-type devices rather than having an independent server switchserving the transaction-type devices.

FIG. 7 illustrates an example method for providing a vending network inaccordance with an embodiment of the invention. In this embodiment, amethod 700 for providing a vending network can be implemented by asystem such as 100 in FIG. 1.

The method 700 can begin at block 702, in which inputs for cashlesstransactions and cash transactions are received from a plurality oftransaction-type devices associated with respective vending machines. Inthe embodiment shown in FIG. 7, one or more transaction-type devices,such as 102A-N, associated with respective vending machines can receiveinputs for cashless transactions and cash transactions.

Block 702 is followed by block 704, in which transaction data associatedwith some or all of the transactions is transmitted to at least oneserver switch. In the embodiment shown in FIG. 7, transaction dataassociated with some or all of the cashless transactions and cashtransactions are transmitted by the transaction-type devices 102A-N to aserver switch, such as 108A.

Block 704 is followed by block 706, in which some or all of thetransactions can be settled via at least one vend settlement server. Inthe embodiment shown in FIG. 7, the server switch 108A can transmit someor all of the transactions to a vend settlement server, such as 116,where some or all of the transactions can be settled or otherwisereconciled. In one embodiment, a server switch such as 108A canassociate a respective reconciliation token with some or all of thetransactions.

The method 700 ends after block 706.

FIG. 8 illustrates another example method for providing a vendingnetwork in accordance with an embodiment of the invention. In thisembodiment, a method 800 for providing a vending network can be can beimplemented by a system such as 100 in FIG. 1.

The method 800 can begin at block 802, in which inputs for cashlesstransactions and cash transactions are received from a plurality oftransaction-type devices associated with respective vending machines. Inthe embodiment shown in FIG. 8, one or more transaction-type devices,such as 102A-N, associated with respective vending machines can receiveinputs for cashless transactions and cash transactions.

Block 802 is followed by block 804, in which transaction data associatedwith some or all of the transactions is transmitted to at least oneserver switch. In the embodiment shown in FIG. 8, transaction dataassociated with some or all of the cashless transactions and cashtransactions are transmitted by the transaction-type devices 102A-N to aserver switch, such as 108A.

Block 804 is followed by block 806, in which a respective reconciliationtoken is associated with some or all of the transactions. In theembodiment shown in FIG. 8, the server switch 108A can associate arespective reconciliation token with some or all of the transactions.

Block 806 is followed by block 808, in which some or all of thetransactions are settled via at least one vend settlement server. In theembodiment shown in FIG. 8, the server switch 108A can transmit some orall of the transactions to a vend settlement server, such as 116, wheresome or all of the transactions can be settled or otherwise reconciled.

The method 800 ends after block 808.

The capabilities of various embodiments of the invention can beimplemented in software, firmware, hardware or some combination thereof.

As one example, one or more aspects of embodiments of the invention canbe implemented in an article of manufacture (e.g., one or more computerprogram products) having, for instance, computer usable media. The mediahas embodied therein, for instance, computer readable program code as ameans for providing and facilitating the capabilities of embodiments ofthe invention. The article of manufacture can be included as a part of acomputer system or sold separately.

Additionally, at least one program storage device readable by a machine,tangibly embodying at least one program of instructions executable bythe machine to perform the capabilities of an embodiment of theinvention can be provided.

The flow diagrams depicted herein are just examples. There may be manyvariations to these diagrams or the elements (or operations) describedtherein without departing from the scope of the invention. For instance,the elements may be performed in a differing order, or elements may beadded, deleted or modified. All of these variations are considered apart of the claimed invention.

While various embodiments of the invention have been described, it willbe understood that those skilled in the art, both now and in the future,may make various improvements and enhancements which fall within thescope of the claims which follow. These claims should be construed tomaintain suitable protection for embodiments of the invention describedherein.

The claimed invention is:
 1. A server comprising: a memory device; aprocessor in communication with the memory device, and configured toexecute a set of instructions to: communicate with a property managementsystem, wherein the server receives transaction data from the propertymanagement system, the transaction data associated with a transactionand comprising a transaction type or a transaction class; inspect eachtransaction type or transaction class; compare each transaction type ortransaction class to one or more allowed transaction types ortransaction classes; and communicate approval of the respectivetransaction when the transaction type or transaction class has beenpreviously approved to perform with the property management system.